| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Hung TuLo
Heavy Asset Relocation Inc
17
   |
Posted - 2011.12.21 18:29:00 -
[1] - Quote
I actually am a professional software quality control analyst.
How may of you in this thread can say that, how many of the players can say that. What do you really know about SQC?
It is virtually impossible to catch every single bug that is in a game this size. Its not possible
1. There are so many computer set-ups that need to be considered.
2. Different graphics cards that are used.
3. Networking issues to consider.
4. Different programing modules that need to be worked on on a daily basis.
5. New equipment that needs to be considered in their systems.
6. They release new code every six months that allow you to enjoy this game. We arn't talking 10 lines of code, we are talking 10's of thousands of lines of code that probably need to be modified.
7. Intigration processes.
8. characters that transfer from one server to other servers.
9. Localization issues.
10. patching issues and when it needs to happen.
11 Release issues.
12. Code upgrades.
13. Code migrations.
14. Petition requests and responses.
15. Server Load issues
That is a small list.
So, when you want to ***** and complain about the patches remember this,. There is alot more than what is going on that you can't see. They have a job just like you should have a job. They are doing their job to the best of their ability and are trying to be a professional as possible.
Don't assume they arn't doing their jobs just because something doesn't work.
Their ability isn't the issue, your attitude is.
"In space all warriors are cold warriors" ----á General Chang-á Star Trek VI |
Hung TuLo
Heavy Asset Relocation Inc
17
|
Posted - 2011.12.21 18:58:00 -
[2] - Quote
HAHAHA,
No I didn't mate but, the work for a SQCA is the same where ever you work. QC on games are different for QC on other companies software. But the USe of control is the same. There are standards that are adhered to. SOmetimes you have to make compromises. Do you stop a major piece of software from being implemented due to a very minor problem? no.
Everything is dependant upon the severity of the problem. Some things go out the door even when there are known issues. That you can't control.
When you are promised something you expect it right? Well when EVE tells you you are getting a release you better get it because 100% of your customers are expecting it. QC can only find so many problems in a timeframe. Even a smaller amount of those items can be fixed at a time. (Time Constriants)
It is easier and better to release something with a small amount of issues than it is to release nothing at all. IF you get a date of release and nothing is release what happenns to the thoughts of the players expecting the release. Opps EVE isn't reliable in their timeframes. That is worse than opps EVE gives us a release ya there are small bugs but we know it will get fixed.
"In space all warriors are cold warriors" ----á General Chang-á Star Trek VI |
Hung TuLo
Heavy Asset Relocation Inc
17
|
Posted - 2011.12.21 20:27:00 -
[3] - Quote
I do understand your point.
Depending on the severity and criticalness of the problem. You don't even thing of placing something into production. And yes you do have those meetings between QA and dev teams.
In the end QA sometimes does not have the "power or control" to sto something from going into production.
It mainly is the 80/20 law or the 90/10 law.
As long as 80% - 90% of the code is working as expected then a push to production is waranted. Once again that depends on the critical nature of the problem. In your example of the UI problem. If the UI was found to be working 95% of the time and the problem was minor. Should the entire push be stopped?
Most of the time. The answer to these things are not your regular QA folks or you dev folks. Its their managers that are answering to the CEO or other bigwigs that will make the ultimate decision. By and large the QA staff is doing their job.
Remember QA just reports the facts. The test the software and report problems, possible causes and possible ramifications.
QA does not cause the coding problems they find them.
Its those in the nosebleed seats that make the decisions.
"In space all warriors are cold warriors" ----á General Chang-á Star Trek VI |
| |
|